…Autoscaling config (ray-project#57260)

In KubeRay v1.5, new structured `Resources` and `Labels` fields will be
added to both the `HeadGroupSpec` and `WorkerGroupSpec` to enable users
to explicitly define these values without relying on `rayStartParams`.
This support is implemented in
ray-project/kuberay#4106. In order for this
change to work with the Ray autoscaler, this PR adds support for
checking the `resources` and `labels` field (with precedence over the
values `rayStartParams` and k8s constainer spec) and generating the
resulting autoscaling config. This change is compatible with older
versions of KubeRay that do not have these new fields, since we fall
back to the previous logic when the top-level fields aren't specified.

Example:

For a group spec specified like this:
```
workerGroupSpecs:
- groupName: worker-group-1
  replicas: 1
  resources:
    GPU: 8
    CPU: 16
  labels:
    ray.io/zone: us-west2-a
    ray.io/region: us-west2
```

The resulting autoscaling config for worker-group-1 would be:
```
"worker-group-1": {
  "labels": {" ray.io/zone": "us-west2-a", " ray.io/region": "us-west2"},
  ...
  "resources": {
    "CPU": 16,
    GPU: 8,
  },
},
``` 

## Related issue number

Contributes to ray-project#51564

---------

Signed-off-by: Ryan O'Leary <[email protected]>

…Autoscaling config (ray-project#57260)

In KubeRay v1.5, new structured `Resources` and `Labels` fields will be
added to both the `HeadGroupSpec` and `WorkerGroupSpec` to enable users
to explicitly define these values without relying on `rayStartParams`.
This support is implemented in
ray-project/kuberay#4106. In order for this
change to work with the Ray autoscaler, this PR adds support for
checking the `resources` and `labels` field (with precedence over the
values `rayStartParams` and k8s constainer spec) and generating the
resulting autoscaling config. This change is compatible with older
versions of KubeRay that do not have these new fields, since we fall
back to the previous logic when the top-level fields aren't specified.

Example:

For a group spec specified like this:
```
workerGroupSpecs:
- groupName: worker-group-1
  replicas: 1
  resources:
    GPU: 8
    CPU: 16
  labels:
    ray.io/zone: us-west2-a
    ray.io/region: us-west2
```

The resulting autoscaling config for worker-group-1 would be:
```
"worker-group-1": {
  "labels": {" ray.io/zone": "us-west2-a", " ray.io/region": "us-west2"},
  ...
  "resources": {
    "CPU": 16,
    GPU: 8,
  },
},
```

## Related issue number

Contributes to ray-project#51564

---------

Signed-off-by: Ryan O'Leary <[email protected]>
Signed-off-by: xgui <[email protected]>

…Autoscaling config (#57260)

In KubeRay v1.5, new structured `Resources` and `Labels` fields will be
added to both the `HeadGroupSpec` and `WorkerGroupSpec` to enable users
to explicitly define these values without relying on `rayStartParams`.
This support is implemented in
ray-project/kuberay#4106. In order for this
change to work with the Ray autoscaler, this PR adds support for
checking the `resources` and `labels` field (with precedence over the
values `rayStartParams` and k8s constainer spec) and generating the
resulting autoscaling config. This change is compatible with older
versions of KubeRay that do not have these new fields, since we fall
back to the previous logic when the top-level fields aren't specified.

Example:

For a group spec specified like this:
```
workerGroupSpecs:
- groupName: worker-group-1
  replicas: 1
  resources:
    GPU: 8
    CPU: 16
  labels:
    ray.io/zone: us-west2-a
    ray.io/region: us-west2
```

The resulting autoscaling config for worker-group-1 would be:
```
"worker-group-1": {
  "labels": {" ray.io/zone": "us-west2-a", " ray.io/region": "us-west2"},
  ...
  "resources": {
    "CPU": 16,
    GPU: 8,
  },
},
``` 

## Related issue number

Contributes to #51564

---------

Signed-off-by: Ryan O'Leary <[email protected]>
Signed-off-by: elliot-barn <[email protected]>

…Autoscaling config (ray-project#57260)

In KubeRay v1.5, new structured `Resources` and `Labels` fields will be
added to both the `HeadGroupSpec` and `WorkerGroupSpec` to enable users
to explicitly define these values without relying on `rayStartParams`.
This support is implemented in
ray-project/kuberay#4106. In order for this
change to work with the Ray autoscaler, this PR adds support for
checking the `resources` and `labels` field (with precedence over the
values `rayStartParams` and k8s constainer spec) and generating the
resulting autoscaling config. This change is compatible with older
versions of KubeRay that do not have these new fields, since we fall
back to the previous logic when the top-level fields aren't specified.

Example:

For a group spec specified like this:
```
workerGroupSpecs:
- groupName: worker-group-1
  replicas: 1
  resources:
    GPU: 8
    CPU: 16
  labels:
    ray.io/zone: us-west2-a
    ray.io/region: us-west2
```

The resulting autoscaling config for worker-group-1 would be:
```
"worker-group-1": {
  "labels": {" ray.io/zone": "us-west2-a", " ray.io/region": "us-west2"},
  ...
  "resources": {
    "CPU": 16,
    GPU: 8,
  },
},
``` 

## Related issue number

Contributes to ray-project#51564

---------

Signed-off-by: Ryan O'Leary <[email protected]>

…Autoscaling config (ray-project#57260)

In KubeRay v1.5, new structured `Resources` and `Labels` fields will be
added to both the `HeadGroupSpec` and `WorkerGroupSpec` to enable users
to explicitly define these values without relying on `rayStartParams`.
This support is implemented in
ray-project/kuberay#4106. In order for this
change to work with the Ray autoscaler, this PR adds support for
checking the `resources` and `labels` field (with precedence over the
values `rayStartParams` and k8s constainer spec) and generating the
resulting autoscaling config. This change is compatible with older
versions of KubeRay that do not have these new fields, since we fall
back to the previous logic when the top-level fields aren't specified.

Example:

For a group spec specified like this:
```
workerGroupSpecs:
- groupName: worker-group-1
  replicas: 1
  resources:
    GPU: 8
    CPU: 16
  labels:
    ray.io/zone: us-west2-a
    ray.io/region: us-west2
```

The resulting autoscaling config for worker-group-1 would be:
```
"worker-group-1": {
  "labels": {" ray.io/zone": "us-west2-a", " ray.io/region": "us-west2"},
  ...
  "resources": {
    "CPU": 16,
    GPU: 8,
  },
},
```

## Related issue number

Contributes to ray-project#51564

---------

Signed-off-by: Ryan O'Leary <[email protected]>
Signed-off-by: Aydin Abiar <[email protected]>

…Autoscaling config (ray-project#57260)

In KubeRay v1.5, new structured `Resources` and `Labels` fields will be
added to both the `HeadGroupSpec` and `WorkerGroupSpec` to enable users
to explicitly define these values without relying on `rayStartParams`.
This support is implemented in
ray-project/kuberay#4106. In order for this
change to work with the Ray autoscaler, this PR adds support for
checking the `resources` and `labels` field (with precedence over the
values `rayStartParams` and k8s constainer spec) and generating the
resulting autoscaling config. This change is compatible with older
versions of KubeRay that do not have these new fields, since we fall
back to the previous logic when the top-level fields aren't specified.

Example:

For a group spec specified like this:
```
workerGroupSpecs:
- groupName: worker-group-1
  replicas: 1
  resources:
    GPU: 8
    CPU: 16
  labels:
    ray.io/zone: us-west2-a
    ray.io/region: us-west2
```

The resulting autoscaling config for worker-group-1 would be:
```
"worker-group-1": {
  "labels": {" ray.io/zone": "us-west2-a", " ray.io/region": "us-west2"},
  ...
  "resources": {
    "CPU": 16,
    GPU: 8,
  },
},
```

## Related issue number

Contributes to ray-project#51564

---------

Signed-off-by: Ryan O'Leary <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>